This PR fixes code fence issues in the .NET metrics and tracing documentation where type names and other technical terms were being over-localized in non-English versions of the documentation.

Problem

As reported in #43876, technical terms like string, int, Boolean, and instrument type names were being translated/localized when the documentation was viewed in other languages, leading to confusing and incorrect translations. For example:

• In Czech: Boolean was over-localized
• In German: string was over-localized
• In Russian: multiple technical terms were incorrectly translated

Solution

Added code fences (backticks) around all type names in the "Type" column of attribute tables across the metrics documentation files. This prevents these technical terms from being localized while still allowing the descriptive text to be properly translated.

Files Changed

• built-in-metrics-system-net.md - Fixed all type names in attribute tables (string → string, int → int)
• built-in-metrics-runtime.md - Fixed all type names in attribute tables
• built-in-metrics-diagnostics.md - Fixed all type names in attribute tables
• distributed-tracing-builtin-activities.md - Already properly formatted from previous PR

Example Change

Before:

| `dns.question.name` | string | The name being queried. | `www.example.com` | Always |

After:

| `dns.question.name` | `string` | The name being queried. | `www.example.com` | Always |

This ensures that string won't be translated to local language equivalents while still allowing the description "The name being queried" to be properly localized.

Fixes #43876.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Internal previews